Golang Job: Senior Back End Engineer

As a Senior Back-end Developer (Golang) at Orbisk, you are responsible for maintaining and developing the back-end of the software platform. Together with the rest of the development-team, you brainstorm about strategic goals and you prepare and implement tickets.

The tickets you receive are for example about Orbisk's customer portal or foodwaste monitor. This customer portal is the most important product and shows customers data about their (future) food waste. The Customer Success team collects all customer feedback and additional input on this portal. For example, a customer might want to be able to measure food waste per guest, or know exactly how long a food waste monitor has been on. When processing these tickets, you discuss with the Front-end Developer and the UX Designer: together you make a plan of what the new feature should look like. You then split this out to the Front-end and Back-end work.

Since code quality and maintainability are important for Orbisk, you keep on striving for structural improvements. It is up to you to optimize the components of the system that are written in Golang (such as API and the foodwaste monitor) with automatic tests and good documentation.

You are part of the development-team and work together with a Front-end Developer, a Full Stack Developer, an Embedded Software Developer, a Product Owner, and the CTO. The whole team works according to the Scrum-method.

"If you enjoy making software platforms as easy as possible for customers, and find it challenging to be responsible for the software of many different departments, then this is a job for you."

Calendar

"On an enjoyable day, you have an extensive planning session with your Scrum team. You discuss the next sprint, and then the goals for the next quarter. The team also gives a lot of input on projects for the roadmap.."

"On a less enjoyable day, you spend a lot of time resolving errors. This is at the expense of the time you can spend on feature development."

Firsthand experience

"You are performing a release of a new feature, but in the afternoon you receive a notification that customers can no longer log into the customer portal. How do you solve this?"

The release seems to be going well, but unfortunately you still receive notifications that it is not working. You approach the Front-end Developer: together you go through the logs to find out where the error is. Once you have found the cause, you have to make a choice: do you revert the release, or do you try to solve the problem?

In this case, you choose the second option. Immediately after that, you will run a test to see if the problem has been resolved. Then you ensure that the release is deployed again.

Growth

At Orbisk, there are several opportunities to grow as an employee. Various courses are offered, allowing you to develop yourself optimally. You work in a fresh and creative start-up, where everyone wants to learn from each-other. Everyone has his own specialization. In the coming years, the organization will also focus on international growth, which means that more and more new positions will become available.

Working at Orbisk

Orbisk is a start-up with a clear mission: to make the global food system more sustainable. The start-up provides complete insights into the food flows of hospitality organisations. Orbisk does this by offering a smart camera and scale that uses image recognition to register which food is thrown away, when and in what quantity. The customer can view this data in the dashboard, which provides insight into food wastage and can be used to reduce it.

What is required?

• A completed bachelor's degree, preferably in Computer Science
• Demonstrable experience with Golang
• Affinity with food waste prevention
• Good command of English, both oral and in writing
• Enthusiastic and motivated

What will you get?

• €4.000 - €6.000 gross p/m (based on knowledge and experience)
• 32 to 40-hour working week
• 30 days of holiday
• Training opportunities
• Pension plan and free lunch at the office

What will you do?

30% Creating and implementing structural improvements

30% Implementing tickets

20% Brainstormen about functionalities

10% Developing sprint tickets

10% Attending sprint sessions